Method and base station for construction of downlink control information format

ABSTRACT

A method and a BS for construction of a DCI format are provided. The method includes configuring a first DAI field of first DCI with a first size and configuring a second DAI field of second DCI with a second size; generating at least one bit with a zero value for one of the first DAI field and the second DAI field if a size difference between the first size and the second size exists; and transmitting, to a UE, an RRC message, the first DCI, and the second DCI, wherein the RRC message includes information for configuring a HARQ-ACK codebook list, the HARQ-ACK codebook list includes a first HARQ-ACK codebook indicated by the first DCI and a second HARQ-ACK codebook indicated by the second DCI, and the first DCI and the second DCI have a same format.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a continuation application of U.S. patentapplication Ser. No. 17/093,030, filed on Nov. 9, 2020, which claims thebenefit of and priority to U.S. Provisional Patent Application Ser. No.62/932,206, filed on Nov. 7, 2019, entitled “Handling of DCI size budgetper serving cell”. The contents of all above-named applications arehereby fully incorporated herein by reference for all purposes.

FIELD

The present disclosure generally relates to wireless communications and,more particularly, to methods and apparatuses for construction of adownlink control information (DCI) format.

BACKGROUND

With the tremendous growth in the number of connected devices and therapid increase in user/Network (NW) traffic volume, various efforts havebeen made to improve different aspects of wireless communication for thenext-generation wireless communication system, such as fifth-generation(5G) New Radio (NR), by improving data rate, latency, reliability, andmobility.

The 5G NR system is designed to provide flexibility and configurabilityto optimize the NW services and types, accommodating various use casessuch as Enhanced Mobile Broadband (eMBB), Massive Machine-TypeCommunication (mMTC), and Ultra-Reliable and Low-Latency Communication(URLLC).

However, as the demand for radio access continues to increase, there isa need in the art to uniform different DCI formats.

SUMMARY

The present disclosure is directed to methods and apparatuses forconstruction of the DCI format.

According to a first aspect of the present disclosure, a methodperformed by a Base Station (BS) is provided for construction of adownlink control information (DCI) format. The method includesconfiguring a first downlink assignment index (DAI) field of first DCIwith a first size and configuring a second DAI field of second DCI witha second size; generating at least one bit with a zero value for one ofthe first DAI field and the second DAI field if a size differencebetween the first size and the second size exists; and transmitting, toa User Equipment (UE), a radio resource control (RRC) message, the firstDCI, and the second DCI, wherein the RRC message includes informationfor configuring a Hybrid Automatic Repeat reQuest-ACKnowledge (HARQ-ACK)codebook list, the HARQ-ACK codebook list includes a first HARQ-ACKcodebook indicated by the first DCI and a second HARQ-ACK codebookindicated by the second DCI, and the first DCI and the second DCI have asame format.

In an implementation of the first aspect, the generated at least one bitwith the zero value forms a most significant bit for the one of thefirst DAI field and the second DAI field.

In another implementation of the first aspect, a first priority of thefirst HARQ-ACK codebook and a second priority of the second HARQ-ACKcodebook are different.

In another implementation of the first aspect, the first HARQ-ACKcodebook and the second HARQ-ACK codebook have different types, and thetypes refer to a semi-static type and a dynamic type.

According to a second aspect of the present disclosure, a Base Station(BS) in a wireless communication system for construction of a downlinkcontrol information (DCI) format is provided. The wireless communicationsystem includes a User Equipment (UE). The BS includes at least oneprocessor; and at least one memory coupled to the at least oneprocessor. The at least one memory stores computer-executableinstructions that, when executed by the at least one processor, causethe BS to configure a first downlink assignment index (DAI) field offirst DCI with a first size and configure a second DAI field of secondDCI with a second size; generate at least one bit with a zero value forone of the first DAI field and the second DAI field if a size differencebetween the first size and the second size exists; and transmit, to theUE, a radio resource control (RRC) message, the first DCI, and thesecond DCI, wherein the RRC message includes information for configuringa Hybrid Automatic Repeat reQuest-ACKnowledge (HARQ-ACK) codebook list,the HARQ-ACK codebook list includes a first HARQ-ACK codebook indicatedby the first DCI and a second HARQ-ACK codebook indicated by the secondDCI, and the first DCI and the second DCI have a same format.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the present disclosure are best understood from the followingwhen read with the accompanying figures. Various features are not drawnto scale. Dimensions of various features may be arbitrarily increased orreduced for clarity of discussion.

FIG. 1 is a flowchart illustrating a DCI format construction procedureperformed by a BS according to an example implementation of the presentdisclosure.

FIG. 2 is a block diagram illustrating a node for wireless communicationaccording to an example implementation the present disclosure.

DESCRIPTION

The following contains specific information pertaining to exemplaryimplementations in the present disclosure. The drawings and theiraccompanying detailed disclosure are directed to merely exemplaryimplementations. However, the present disclosure is not limited tomerely these exemplary implementations. Other variations andimplementations of the present disclosure will occur to those skilled inthe art. Unless noted otherwise, like or corresponding elements amongthe figures may be indicated by like or corresponding referencenumerals. Moreover, the drawings and illustrations in the presentdisclosure are generally not to scale and are not intended to correspondto actual relative dimensions.

The following contains specific information pertaining to exampleimplementations in the present disclosure. The drawings and theiraccompanying detailed disclosure are directed to merely exampleimplementations. However, the present disclosure is not limited tomerely these example implementations. Other variations andimplementations of the present disclosure will occur to those skilled inthe art. Unless noted otherwise, like or corresponding elements amongthe figures may be indicated by like or corresponding referencenumerals. Moreover, the drawings and illustrations in the presentdisclosure are generally not to scale and are not intended to correspondto actual relative dimensions.

For consistency and ease of understanding, like features are identified(although, in some examples, not illustrated) by numerals in the examplefigures. However, the features in different implementations may differin other respects, and thus shall not be narrowly confined to what isillustrated in the figures.

References to “one implementation,” “an implementation,” “exampleimplementation,” “various implementations,” “some implementations,”“implementations of the present disclosure,” etc., may indicate that theimplementation(s) of the present disclosure may include a particularfeature, structure, or characteristic, but not every possibleimplementation of the present disclosure necessarily includes theparticular feature, structure, or characteristic. Further, repeated useof the phrase “in one implementation,” “in an example implementation,”or “an implementation,” do not necessarily refer to the sameimplementation, although they may. Moreover, any use of phrases like“implementations” in connection with “the present disclosure” are nevermeant to characterize that all implementations of the present disclosuremust include the particular feature, structure, or characteristic, andshould instead be understood to mean “at least some implementations ofthe present disclosure” include the stated particular feature,structure, or characteristic. The term “coupled” is defined asconnected, whether directly or indirectly through interveningcomponents, and is not necessarily limited to physical connections. Theterm “comprising,” when utilized, means “including, but not necessarilylimited to”; it specifically indicates open-ended inclusion ormembership in the so-disclosed combination, group, series, and theequivalent.

The term “and/or” herein is only an association relationship fordescribing associated objects, and represents that three relationshipsmay exist, for example, A and/or B may represent that A exists alone, Aand B exist at the same time, and B exists alone. “A and/or B and/or C”may represent that at least one of A, B and C exists. In addition, thecharacter “/” used herein generally represents that the former andlatter associated objects are in an “or” relationship.

Additionally, for the purpose of non-limiting explanation, specificdetails, such as functional entities, techniques, protocols, standards,and the like, are set forth for providing an understanding of thedisclosed technology. In other examples, a detailed disclosure ofwell-known methods, technologies, systems, architectures, and the likeare omitted in order not to obscure the present disclosure withunnecessary details.

Persons skilled in the art will immediately recognize that any NWfunction(s) or algorithm(s) in the present disclosure may be implementedby hardware, software, or a combination of software and hardware.Disclosed functions may correspond to modules that may be software,hardware, firmware, or any combination thereof. The softwareimplementation may include computer-executable instructions stored oncomputer-readable media, such as memory or other types of storagedevices. For example, one or more microprocessors or general-purposecomputers with communication processing capability may be programmedwith corresponding executable instructions and carry out the disclosedNW function(s) or algorithm(s). The microprocessors or general-purposecomputers may be formed of Application-Specific Integrated Circuits(ASICs), programmable logic arrays, and/or one or more Digital SignalProcessor (DSPs). Although some of the example implementations in thepresent disclosure are directed to software installed and executing oncomputer hardware, alternative example implementations implemented asfirmware, as hardware, or as a combination of hardware and software arewell within the scope of the present disclosure.

The computer-readable medium includes, but is not limited to, RandomAccess Memory (RAM), Read-Only Memory (ROM), Erasable ProgrammableRead-Only Memory (EPROM), Electrically Erasable Programmable Read-OnlyMemory (EEPROM), flash memory, Compact Disc Read-Only Memory (CD-ROM),magnetic cassettes, magnetic tape, magnetic disk storage, or any otherequivalent medium capable of storing computer-readable instructions.

A radio communication NW architecture (e.g., a Long-Term Evolution (LTE)system, an LTE-Advanced (LTE-A) system, or an LTE-Advanced Pro system)typically includes at least one Base Station (BS), at least one userequipment (UE), and one or more optional NW elements that provideconnection towards an NW. The UE communicates with the NW (e.g., a CoreNW (CN), an Evolved Packet Core (EPC) NW, an Evolved UniversalTerrestrial Radio Access NW (E-UTRAN), a Next-Generation Core (NGC), oran Internet), through a Radio Access NW (RAN) established by the BS.

It should be noted that, in the present disclosure, a UE may include,but is not limited to, a mobile station, a mobile terminal or device, ora user communication radio terminal. For example, a UE may be a portableradio equipment, which includes, but is not limited to, a mobile phone,a tablet, a wearable device, a sensor, or a Personal Digital Assistant(PDA) with wireless communication capability. The UE is configured toreceive and transmit signals over an air interface to one or more cellsin a RAN.

A BS may include, but not limited to, a Node B (NB) as in the UniversalMobile Telecommunication System (UMTS), an evolved Node B (eNB) as inthe LTE-A, a Radio NW Controller (RNC) as in the UMTS, a Base StationController (BSC) as in the Global System for Mobile communications(GSM)/GSM EDGE (Enhanced Data rates for GSM Evolution) Radio Access NW(GERAN), a Next Generation eNB (ng-eNB) as in an E-UTRA BS in connectionwith the 5GC, a next-generation Node B (gNB) as in the 5G Access NW(5G-AN), and any other apparatus capable of controlling radiocommunication and managing radio resources within a cell. The BS mayconnect to serve the one or more UEs through a radio interface to theNW.

A BS may be configured to provide communication services according to atleast one of the following Radio Access Technologies (RATs): WorldwideInteroperability for Microwave Access (WiMAX), GSM (often referred to as2G), GERAN, General Packet Radio Service (GPRS), UMTS (often referred toas 3G) based on basic Wideband-Code Division Multiple Access (W-CDMA),High-Speed Packet Access (HSPA), LTE, LTE-A, enhanced LTE (eLTE), NR(often referred to as 5G), and LTE-A Pro. However, the scope of thepresent disclosure should not be limited to the protocols previouslydisclosed.

The BS may be operable to provide radio coverage to a specificgeographical area using a plurality of cells included in the RAN. The BSmay support the operations of the cells. Each cell is operable toprovide services to at least one UE within its radio coverage. Morespecifically, each cell (often referred to as a serving cell) mayprovide services to serve one or more UEs within its radio coverage,(e.g., each cell schedules the Downlink (DL) and optionally Uplink (UL)resources to at least one UE within its radio coverage for DL andoptionally UL packet transmissions). The BS may communicate with one ormore UEs in the radio communication system through the plurality ofcells. A cell may allocate sidelink (SL) resources for supportingproximity service (ProSe). Each cell may have overlapped coverage areaswith other cells. In Multi-RAT Dual Connectivity (MR-DC) cases, theprimary cell of a Master Cell Group (MCG) or a Secondary Cell Group(SCG) may be called a Special Cell (SpCell). A Primary Cell (PCell) mayrefer to the SpCell of an MCG. A PSCell may refer to the SpCell of anSCG. MCG refers to a group of serving cells associated with the MasterNode (MN), including the SpCell and optionally one or more secondarycells (SCells). SCG refers to a group of serving cells associated withthe Secondary Node (SN), including the SpCell and optionally one or moreSCells.

As previously disclosed, the frame structure for NR is to supportflexible configurations for accommodating various next-generation (e.g.,5G) communication requirements, such as eMBB, mMTC, and URLLC, whilefulfilling high reliability, high data rate, and low latencyrequirements. The orthogonal frequency-division multiplexing (OFDM)technology, as agreed in the 3^(rd) Generation Partnership Project(3GPP), may serve as a baseline for an NR waveform. The scalable OFDMnumerology, such as the adaptive sub-carrier spacing, the channelbandwidth, and the cyclic prefix (CP), may also be used. Additionally,two coding schemes are considered for NR: (1) low-density parity-check(LDPC) code and (2) polar code. The coding scheme adaption may beconfigured based on the channel conditions and/or service applications.

Moreover, it is also considered that in a transmission time interval ofa single NR frame, at least DL transmission data, a guard period, and ULtransmission data should be included, where the respective portions ofthe DL transmission data, the guard period, and the UL transmission datashould also be configurable, for example, based on the NW dynamics ofNR. In addition, SL resources may also be provided in an NR frame tosupport ProSe services.

In order to reduce device complexity, ‘3+1’ Downlink Control Information(DCI) size budget is defined in the Rel-15 3GPP specification. In otherwords, as shown in Table 1, one UE (or another similar device) at mostmonitors three different DCI sizes using a Cell-Radio Network TemporaryIdentifier (C-RNTI) and one DCI size using other RNTIs. For followingthe DCI size budget per serving cell of the UE, the DCI size alignmentis the procedure to ensure that the limitation is satisfied. In NRRel-16, a possible smaller DCI size and a new DCI format for schedulingUltra-Reliability Low-Latency Communication (URLLC) data may beintroduced. Specially, a bitfield width in new DCI format fields maybecome configurable. Also, one new DCI format for indicating thecancellation of uplink transmission may be introduced for URLLC. Also,for a power saving purpose, one new DCI format for providing anindication of power saving information used outside an active time maybe introduced.

TABLE 1 non-C-RNTI C-RNTI C-RNTI C-RNTI (size 1) (size 2) (size 3) (size4) DCI Monitored in Monitored in format Common UE specific 0-0 Search SS(USS) Space (CSS) Apply Apply configured initial UL ULBWP Bandwidth Part(BWP) DCI Monitored format in USS 0-1 Apply configured UL BWP DCIMonitored Monitored in format in CSS USS 1-0 Apply Apply size ofconfigured Control DL BWP Resource Set (CORESET) 0 or initial DL BWP DCIMonitored format in USS 1-1 Apply configured DL BWP

It has been agreed that the maximum time domain resource allocation(TDRA) table size is increased to 64 for non-slot based Physical UplinkShared Channel (PUSCH) repetition transmission for NR URLLC. Also, ithas been agreed that the number of bits for a carrier indicator in thenew DCI format for DL scheduling and the new DCI format for ULscheduling can be separately configured.

Besides, it has been agreed that up to two Hybrid Automatic RepeatreQuest-ACKnowledge (HARQ-ACK) codebooks can be simultaneously generatedfor supporting different service types for a UE; in other words,PDSCH-HARQ-ACK-Codebook can be separately configured for a UE. To put itanother way, different types of HARQ-ACK codebook may be configured inthe PUCCH-Config.

The introduction of the new DCI for scheduling URLLC data (e.g., DCIformat 0-2, DCI format 1-2, DCI format 2-4) may need further rules forDCI size alignment. Since most of the bitfield sizes in the new DCIformat are configurable, it may lead to increased varieties of DCIsizes. Thus, an enhanced DCI size budget and the detailed DCI sizealignment should be defined. It is not clear how to align a new DCIformat size with a legacy DCI format, so detailed procedures should beintroduced to the 3GPP specification. Furthermore, the DCI size foroutside active time (e.g., DCI format 2-6 for scheduling power savingindication) also needs to be taken into consideration. In addition,rather than configuring a cell group specific HARQ-ACK codebook type,configuring a Physical Uplink Control Channel (PUCCH)-resource specificHARQ-ACK codebook type becomes possible. Also, intra-slot based PUSCHrepetition transmission supports a larger size of TDRA table.Furthermore, a configurable number of bits for a carrier indicator inthe new DCI format means that the carrier indicator for DL schedulingand UL scheduling can be separately configured. In other words, when thePhysical Downlink Shared Channel (PDSCH)-HARQ-ACK-Codebook is separatelyconfigured for a UE, a PUSCH TDRA size is increased to 64 and aredundancy version (RV) number becomes configurable, which may lead tosome impact on the DCI field (e.g., downlink assignment index (DAI),TDRA, RV). Thus, the solutions to the problem caused from theconfigurable DCI field need to be further clarified.

In some implementations of the present disclosure, a new DCI format usedfor scheduling URLLC data (but used for scheduling other service type isnot precluded) may be DCI format 1-2 (for DL) and DCI format 0-2 (forUL), respectively. In some implementations of the present disclosure, anew DCI format used for notifying the resources where UE may cancel acorresponding UL transmission from the UE may be DCI format 2-4. In someimplementations of the present disclosure, a new DCI format used forindicating power saving information outside the active time may be DCIformat 2-6.

The enhanced DCI size budget and detailed implementations for the DCIsize alignment may be as presented hereinafter with solutions A and B.

Solution A. The DCI size budget may remain the same as the value inRel-15 (e.g., the ‘3+1’ based on some pre-defined conditions), and themethod to differentiate DCI format with the same payload size may befurther clarified in the following:

-   -   A1. The payload size of the DCI format 1-0 equals that of the        DCI format 0-0; the payload size of the DCI format 1-1 equals        that of the DCI format 0-1; and the payload size of the DCI        format 1-2 equals that of the DCI format 0-2.    -   A2. The payload size of the DCI format 1-0 equals that of the        DCI format 0-0; the payload size of the DCI format 1-2 equals        that of the DCI format 0-2; and the payload size of the DCI        format 1-0/0-0 equals that of the DCI format 1-2/0-2.    -   A3. The payload size of the DCI formats 1-0 equals that of the        DCI format 0-0; the payload size of the DCI format 1-2 equals        that of the DCI format 1-1; and the payload size of the DCI        format 0-2 equals that of the DCI format 0-1.    -   A4. Regardless of whether the DCI format 1-0/0-0 is monitored in        the CSS or in the USS, the payload size of the DCI format 1-0        equals that of the DCI format 0-0 monitored in the CSS; and the        payload size of the DCI format 1-2 equals that of the DCI format        0-2.

Solution B. The value of the DCI size budget may be enhanced to ‘4+1’ or‘3+2’ without conditions or based on the reported UE capability or somepre-defined conditions in the following:

-   -   B1. For the value of DCI size budget being ‘4+1’, the payload        size of the DCI format 1-0 equals that of the DCI format 0-0;        and the payload size of the DCI format 1-2 equals that of the        DCI format 0-2.    -   B2. For the value of DCI size budget being ‘4+1’, regardless of        whether the DCI format 1-0/0-0 is monitored in the CSS or in the        USS, the payload size of the DCI format 1-0 equals that of the        DCI format 0-0 monitored in the CSS.    -   B3. For the value of DCI size budget being ‘3+2’, the payload        size of the DCI formats configured outside the active time        (e.g., the DCI format 2-6) and the payload size of the DCI        formats configured inside the active time may be counted        together. Accordingly, the above-mentioned procedure(s) of the        DCI size alignment (e.g., the procedure for the DCI budget        ‘3+1’) may be applied while the UE monitors three different DCI        sizes using the C-RNTI and two different DCI sizes using other        Radio Network Temporary Identifier (RNTI), e.g., Power Saving        (PS)-RNTI. More details are presented in the following:        -   B3-1. The value of DCI size budget of ‘3+2’ or ‘3+1’ may be            utilized, which may depend on whether the DCI format 2-6 or            other DCI format outside the active time may be configured            or not.        -   B3-2. If there are two or more different sizes for the DCI            format 2-6, one of the payload sizes of the DCI format 2-6            is to be aligned with the DCI format 2-0/2-1/2-4/1-0/0-0. It            should be noted that the DCI format 1-0/0-0 may be monitored            in the CSS.        -   B3-3. The payload size of the DCI format 2-1 is to be            aligned with that of the DCI format 2-4 based on certain            conditions.

The following presents the impacts on the DCI format field. It isbecause the payload size of the DCI format for initial transmission fortype2 configured grant configuration or for semi-persistent schedulingmay need to be the same as that of the DCI format for re-transmission(e.g. the DCI format scrambled with Configured Scheduling (CS)-RNTI andthe DCI format scrambled with C-RNTI). Furthermore, some field(s)position may need to be aligned between the DCI format for initialtransmission and the DCI format for re-transmission. Also, aligning thesize of configurable fields between different DCI formats may decreasethe varieties of DCI size.

First, if there are different types of PDSCH-HARQ-ACK-Codebook (e.g.,semi-static type and/or dynamic type) configured to the UE, a size of adownlink assignment indicator (DAI) field may equal that of the DCI forscheduling data corresponding to the Type 2 HARQ-ACK codebook.Specifically, Type1 HARQ-ACK codebook is referred to as semi-staticHARQ-ACK codebook and Type 2 HARQ-ACK codebook is referred to as dynamicHARQ-ACK codebook, respectively. Second, if a priority indication fieldis configured, the size of the field may be the same between differentDCI formats and/or the same DCI formats scrambled with different RNTIs.Third, for the TDRA field and the RV field, if the Rel-16 PUSCH schemeis configured, the size of the field may align with the maximum size ofthe field between different DCI formats and/or the same DCI formatsscrambled with different RNTIs.

More detailed disclosures/solutions/embodiments/examples/methods arepresented in the following. Noticeably, any two or more than two of thefollowing paragraphs, solutions, embodiments, methods, examples,operations, points, actions, behaviors, terms, or claims described inthe following may be combined logically, reasonably, and properly toform a specific method. Any sentence, paragraph, solutions, embodiments,methods, examples, operations, point, action, behaviors, terms, orclaims described in the following may be implemented independently andseparately to form a specific method. Dependency, e.g., “based on”,“more specifically”, “preferably”, “in one embodiment”, or etc., in thefollowing disclosure is just one possible example which would notrestrict the specific method.

Implementations of the present disclosure include enhancing the DCI sizebudget. Specifically, the possible DCI size budget may need someenhancements. In one example, the DCI size budget remains the same asthat of Rel-15. Preferably, the total number of different DCI sizesconfigured to monitor may be 4 for a cell. Specifically, the number ofdifferent DCI sizes scrambled with C-RNTI configured to monitor may be 3and the number of DCI size scrambled with other RNTIs configured tomonitor may be 1 for the cell.

In one example, the DCI size budget enhances to 5. In one aspect of thisexample, the total number of different DCI sizes configured to monitormay be 5 for a cell. Specifically, the number of different DCI sizesscrambled with C-RNTI configured to monitor may be 4 and the number ofDCI sizes scrambled with other RNTIs configured to monitor may be 1 forthe cell. In another aspect of this example, the total number ofdifferent DCI sizes configured to monitor may be 5 for a cell.Specifically, the number of different DCI sizes scrambled with C-RNTIconfigured to monitor may be 3 and the number of DCI sizes scrambledwith other RNTIs configured to monitor may be 2 for the cell.

In some of the embodiments, the DCI size budget may be determinedexplicitly based on reported UE capability. In one example, the UE mayreport the exact supported DCI size budget, and then the UE may notexpect to handle a configuration that results in the total number ofdifferent DCI sizes configured to monitor being more than this value forthe cell. In another example, the UE may indicate a capability which isused for indicating whether to support different service types for thecell based on this capability, and then the UE may not expect to handlea configuration that results in the total number of different DCI sizesconfigured to monitor being more than a value or within a range for thecell. In another example, the UE may indicate several capabilities(e.g., the DCI budget ‘3+1’ and ‘4+1’) and the applied DCI budget may beup to the gNB's configuration. More specifically, if the DCI budget‘3+1’ is applied, the gNB may not configure such scheduling associatedwith the DCI budget ‘4+1’ to the UE.

In some of the embodiments, the DCI size budget may be determinedimplicitly based on some conditions. In one example, the DCI size budget‘3+1’ may be applied as a default value for the UE when the UE isconfigured to a power saving mode explicitly or implicitly. Morespecifically, if the DCI size budget ‘4+1’ may be applied to the UEoriginally, the UE may fall back to a default state (e.g., the DCIbudget ‘3+1’) after receiving some indications or configurations.

Again, in some of the embodiments, the DCI size budget may be determinedimplicitly based on some conditions. In another example, the DCI sizebudget may depend on a capability for indicating URLLC service, powersaving service, or other types of service having different requirements.More details are presented in the following scenarios.

In one aspect of these examples, the DCI size budget may depend on PDCCHmonitoring capability reported by the UE. The PDCCH monitoringcapability may indicate whether URLLC data is scheduled or not, so theDCI size budget may be larger when some specific monitoring spans aresupported (e.g., PDCCH monitoring span (2,2)). Otherwise, it may beunnecessary to increase the DCI size budget.

In one aspect of these examples, the DCI size budget may depend onwhether the new DCI format (e.g., DCI format 0-2/DCI format 1-2/DCIformat 2-4/DCI format 2-6) is configured on the same carrier or not.

In one aspect of these examples, the DCI size budget may depend onwhether different minimum PDSCH processing time capabilities on the samecarrier are supported or not.

In one aspect of these examples, the DCI size budget may depend onwhether out-of-order on the same carrier is supported or not.

In one aspect of these examples, the DCI size budget may depend onwhether intra-slot based PUSCH repetition transmission (e.g., the PUSCHtransmission scheme in Rel-16) on the same carrier is supported or not.

In one aspect of these examples, the DCI size budget may depend onwhether multiple configured grant/Semi-Persistent Scheduling (SPS)configurations on the same carrier are supported or not.

In one aspect of these examples, the DCI size budget may depend onwhether cross-slot scheduling on the same carrier is supported or not.

In one aspect of these examples, the DCI size budget may depend onwhether PDCCH based indication for power saving information configuredoutside the active time on the same carrier is supported or not.

In one aspect of these examples, the DCI size budget may depend onwhether the scheduled data or the DCI is configured in the specific BWPor in a default BWP to the UE.

In one aspect of these examples, the DCI size budget may depend onwhether the UE is configured to a long Discontinuous Reception (DRX)state.

Implementations of the present disclosure include enhancing the DCI sizealignment. Specifically, the DCI budget is equal to the DCI budget‘3+1’. If necessary, padding or truncation may be applied to the DCIformats, and more details are presented in the following embodiments.

In one example, if the DCI budget ‘3+1’ is applied, the payload size ofthe DCI format 1-0 equals that of the DCI format 0-0; the payload sizeof the DCI formats 1-1 equals that of the DCI format 0-1; and thepayload size of the DCI format 1-2 equals that of the DCI format 0-2.Example implementations are presented in Table 2.

TABLE 2 non-C-RNTI (size 1) or C-RNTI C-RNTI C-RNTI C-RNTI (size 2)(size 3) (size 4) DCI format Monitored Monitored 0-0 in CSS in USS ApplyApply initial configured UL BWP UL BWP DCI format Monitored 0-1 in USSApply configured UL BWP DCI format Monitored 0-2 in USS Apply configuredUL BWP DCI format Monitored in Monitored 1-0 CSS in USS Apply Apply sizeof configured CORESET DL BWP 0 or initial DL BWP DCI format Monitored1-1 in USS Apply configured DL BWP DCI format Monitored 1-2 in USS Applyconfigured DL BWP

In one example, if the DCI budget ‘3+1’ is applied, the payload size ofthe DCI format 1-0 equals that of the DCI format 0-0; the payload sizeof the DCI format 1-2 equals that of the DCI format 0-2; and the payloadsize of the DCI format 1-0/0-0 equals that of the DCI format 1-2/0-2.Example implementations are presented in Table 3.

TABLE 3 non-C-RNTI (size 1) or C-RNTI C-RNTI C-RNTI C-RNTI (size 2)(size 3) (size 4) DCI format Monitored Monitored 0-0 in CSS in USS ApplyApply initial configured UL BWP UL BWP DCI format Monitored 0-1 in USSApply configured UL BWP DCI format Monitored 0-2 in USS Apply configuredUL BWP DCI format Monitored Monitored 1-0 in CSS in USS Apply Apply sizeof configured CORESET 0 DL BWP or initial DL BWP DCI format Monitored1-1 in USS Apply configured DL BWP DCI format Monitored 1-2 in USS Applyconfigured DL BWP

As can be seen in Table 3, in one aspect of this example, the payloadsize of the DCI format 1-0/0-0 may be the same as that of DCI format1-2/0-2, and both may be scrambled with C-RNTI, and accordingly, it mayneed more clarification on how to differentiate DCI formats with thesame size. A new field in DCI format (e.g., an identifier) may be used.For example, ‘0’ may refer to DCI format 1-0/0-0; and ‘1’ may refer toDCI format 1-2/0-2. In another example, ‘0’ may refer to DCI format1-2/0-2; and ‘1’ may refer to DCI format 1-0/0-0.

In another aspect of this example, it may use a new field that is usedto indicate the priority in the DCI format. For example, ‘0’ may referto DCI format 1-0/0-0; and ‘1’ may refer to DCI format 1-2/0-2. Inanother example, ‘0’ may refer to DCI format 1-2/0-2; and ‘1’ may referto DCI format 1-0/0-0.

In one aspect of this example, it may use a new RNTI or ModulationCoding Scheme-Cell (MCS-C)-RNTI that is used to differentiate thepriority for the DCI format. For example, if payload size of the DCIformat 1-0/0-0 is the same as that of the DCI format 1-2/0-2, one of theDCI formats may be scrambled with new-RNTI or MCS-C-RNTI, and the DCIformat scrambled with new-RNTI or MCS-C-RNTI may refer to DCI format1-2/0-2. in another example, the DCI format scrambled with new-RNTI orMCS-C-RNTI may refer to DCI format 1-0/0-0.

In one aspect of this example, the CORESET or search space may beutilized. For example, DCI format 1-0/0-0 may be monitored in differentCORESETs/search spaces from DCI format 1-2/0-2. Another example may bethat a specific CORESET ID or search space ID may refer to different DCIformats. Moreover, the DCI format 1-2/0-2 may be configured to thesmaller CORESET ID/search space ID, and vice versa.

In one embodiment, if the DCI budget ‘3+1’ is applied, the payload sizeof the DCI format 1-0 equals that of the DCI format 0-0; the payloadsize of the DCI formats 1-2 equals that of the DCI format 1-1; and thepayload size of the DCI formats 0-2 equals that of the DCI format 0-1.Detailed implementations are presented in Table 4.

TABLE 4 non-C-RNTI (size 1) or C-RNTI C-RNTI C-RNTI C-RNTI (size 2)(size 3) (size 4) DCI format Monitored Monitored 0-0 in CSS in USS ApplyApply initial configured UL BWP UL BWP DCI format Monitored 0-1 in USSApply configured UL BWP DCI format Monitored 0-2 in USS Apply configuredUL BWP DCI format Monitored Monitored 1-0 in CSS in USS Apply Apply sizeof configured CORESET 0 DL BWP or initial DL BWP DCI format Monitored1-1 in USS Apply configured DL BWP DCI format Monitored 1-2 in USS Applyconfigured DL BWP

As can be seen in Table 4, in one aspect of this example, the payloadsize of the DCI format 1-1 may be the same as that of DCI format 1-2,and the payload size of the DCI format 0-1 may be the same as that ofDCI format 0-2, respectively, and accordingly, it may need moreclarification on how to differentiate DCI formats with the same size. Anew field in DCI format (e.g., an identifier) may be used. For example,‘0’ may refer to DCI format 1-1/0-1; and ‘1’ may refer to DCI format1-2/0-2, and vice versa.

In one aspect of this example, it may use a new field that is used toindicate the priority in the DCI format. For example, ‘0’ may refer toDCI format 1-1/0-1; and ‘1’ may refer to DCI format 1-2/0-2, and viceversa.

In one aspect of this example, it may use a new-RNTI or MCS-C-RNTI thatis used to differentiate the priority for the DCI format. For example,if the payload size of the DCI format 1-1/0-1 is the same as that of theDCI format 1-2/0-2, one of the DCI formats may be scrambled withnew-RNTI or MCS-C-RNTI, and the DCI format scrambled with new-RNTI orMCS-C-RNTI may refer to DCI format 1-2/0-2, and vice versa.

In one aspect of this example, it may use the CORESET or search space.For example, DCI format 1-1/0-1 may be monitored in differentCORESETs/search spaces from the DCI format 1-2/0-2. Another example maybe that a specific CORESET ID or search space ID may refer to adifferent DCI format. Moreover, the DCI format 1-2/0-2 may be configuredto the smaller CORESET ID/search space ID, and vice versa.

In one embodiment, if the DCI budget ‘3+1’ is applied, regardless ofwhether the DCI format 1-0/0-0 is monitored in the CSS or in the USS,the payload size of the DCI format 1-0 equals that of the DCI format 0-0monitored in the CSS. In other words, it is disclosed to align thepayload size of DCI format 1-0/0-0 monitored in the CSS and that of DCIformat 1-0/0-0 monitored in the USS, and the payload size of DCI format1-0/0-0 monitored in the USS is given based on an initial BWP or thesize of CORESET 0. In addition, the payload size of the DCI format 1-2equals that of the DCI format 0-2. Example implementations are presentedin Table 5.

TABLE 5 non-C-RNTI (size 1) or C-RNTI C-RNTI C-RNTI C-RNTI (size 2)(size 3) (size 4) DCI format Monitored 0-0 in CSS or USS (C-RNTI) Applyinitial UL BWP DCI format Monitored 0-1 in USS Apply configured UL BWPDCI format Monitored 0-2 in USS Apply configured UL BWP DCI formatMonitored 1-0 in CSS or USS (C-RNTI) Apply size of CORESET 0 or initialDL BWP DCI format Monitored 1-1 in USS Apply configured DL BWP DCIformat Monitored 1-2 in USS Apply configured DL BWP

Implementations of the present disclosure includes performing a DCI sizealignment procedure for the DCI budget being equal to ‘3+1’. In oneexample, the DCI size alignment procedure may be applied according tothe following six actions (e.g., Action 0 through Action 5 as presentedbelow). Noticeably, in one embodiment, each action in the procedure maybe arbitrarily combined or exchanged. Also, in one embodiment, the DCIsize alignment for the DCI format 1-2 and the DCI format 0-2 may beproceeded before or after the UE performs the DCI size alignment for theDCI format 0-0 and the DCI format 1-0, and/or for the DCI format 0-1 andthe DCI format 1-1.

In one embodiment, the following actions may be an example to perform aDCI size alignment procedure for Table 2.

Action 0:

It may be disclosed to determine the DCI format 0-0 monitored in the CSSbased on the given configuration (e.g., SearchSpace-Config,PDCCH-Config) and/or RNTI, and the DCI format size may be related to theinitial UL BWP.

It may be disclosed to determine the DCI format 1-0 monitored in the CSSbased on the given configuration (e.g., SearchSpace-Config,PDCCH-Config) and/or RNTI, and the DCI format size may be related to (1)the size of the CORESET 0 if the CORESET 0 is configured for the cell;and (2) the size of an initial DL bandwidth part if the CORESET 0 is notconfigured for the cell.

If the DCI format 0-0 is monitored in the CSS and if the number ofinformation bits in the DCI format 0-0 prior to padding is less than thepayload size of the DCI format 1-0 monitored in the CSS for schedulingthe same serving cell, a number of zero padding bits may be generatedfor the DCI format 0-0 until the payload size equals that of the DCIformat 1-0.

If the DCI format 0-0 is monitored in the CSS and if the number ofinformation bits in the DCI format 0-0 prior to truncation is largerthan the payload size of the DCI format 1-0 monitored in the CSS forscheduling the same serving cell, the bit-width of the frequency domainresource assignment field in the DCI format 0-0 may be reduced bytruncating the first few most significant bits such that the size of DCIformat 0-0 equals the size of the DCI format 1-0.

Action 1:

It may be disclosed to determine the DCI format 0-0 monitored in the USSbased on the given configuration (e.g., SearchSpace-Config,PDCCH-Config) and/or RNTI, and the DCI format size may be related to thesize of the active UL BWP.

It may be disclosed to determine the DCI format 1-0 monitored in the USSbased on the given configuration (e.g., SearchSpace-Config,PDCCH-Config) and/or RNTI, and the DCI format size may be related to thesize of the active DL BWP.

For the UE configured with supplementary Uplink in ServingCellConfig ina cell, if the PUSCH is configured to be transmitted on both thesupplementary UL (SUL) and the non-SUL of the cell and if the number ofinformation bits in the DCI format 0-0 in the USS for the SUL is notequal to the number of information bits in the DCI format 0-0 in the USSfor the non-SUL, a number of zero padding bits may be generated for thesmaller DCI format 0-0 until the payload size equals that of the largerDCI format 0-0.

If the DCI format 0-0 is monitored in the USS and if the number ofinformation bits in the DCI format 0-0 prior to padding is less than thepayload size of the DCI format 1-0 monitored in the USS for schedulingthe same serving cell, a number of zero padding bits may be generatedfor the DCI format 0-0 until the payload size equals that of the DCIformat 1-0.

If the DCI format 1-0 is monitored in the USS and if the number ofinformation bits in the DCI format 1-0 prior to padding is less than thepayload size of the DCI format 0-0 monitored in the USS for schedulingthe same serving cell, zeros may be appended to the DCI format 1-0 untilthe payload size equals that of the DCI format 0-0.

Action 2:

It may be disclosed to determine the DCI format 0-1 monitored in the USSbased on the given configuration (e.g., SearchSpace-Config,PDCCH-Config) and/or RNTI, and the DCI format size may be related to thesize of the active UL BWP.

It may be disclosed to determine the DCI format 1-1 monitored in the USSbased on the given configuration (e.g., SearchSpace-Config,PDCCH-Config) and/or RNTI, and the DCI format size may be related to thesize of the active DL BWP.

For the UE configured with supplementary Uplink in ServingCellConfig ina cell, if the PUSCH is configured to be transmitted on both the SUL andthe non-SUL of the cell and if the number of information bits in the DCIformat 0-1 for the SUL is not equal to the number of information bits inthe DCI format 0-1 for the non-SUL, zeros may be appended to the smallerDCI format 0-1 until the payload size equals that of the larger DCIformat 0-1.

If the size of the DCI format 0-1 monitored in the USS equals that ofthe DCI format 0-0/1-0 monitored in another USS, one bit of zero paddingmay be appended to the DCI format 0-1.

If the size of the DCI format 1-1 monitored in the USS equals that ofthe DCI format 0-0/1-0 monitored in another USS, one bit of zero paddingmay be appended to the DCI format 1-1.

Action 3:

It may be disclosed to determine the DCI format 0-2 monitored in the USSbased on the given configuration (e.g., SearchSpace-Config,PDCCH-Config) and/or RNTI, and the DCI format size may be related to thesize of the active UL BWP.

It may be disclosed to determine the DCI format 1-2 monitored in the USSbased on the given configuration (e.g., SearchSpace-Config,PDCCH-Config) and/or RNTI, and the DCI format size may be related to thesize of the active DL BWP.

For the UE configured with supplementary Uplink in ServingCellConfig ina cell, if the PUSCH is configured to be transmitted on both the SUL andthe non-SUL of the cell and if the number of information bits in the DCIformat 0-2 for the SUL is not equal to the number of information bits inDCI format 0-2 for the non-SUL, bits with value set to zero may beappended to the smaller DCI format 0-2 until the payload size equalsthat of the larger DCI format 0-2.

If the DCI format 0-2 is monitored in USS and if the number ofinformation bits in the DCI format 0-2 prior to padding is less than thepayload size of the DCI format 1-2 monitored in the USS for schedulingthe same serving cell, a number of zero padding bits may be generatedfor the DCI format 0-2 until the payload size equals that of the DCIformat 1-2.

If the DCI format 1-2 is monitored in the USS and if the number ofinformation bits in the DCI format 1-2 prior to padding is less than thepayload size of the DCI format 0-2 monitored in the USS for schedulingthe same serving cell, a number of zero padding bits may be appended tothe DCI format 1-2 until the payload size equals that of the DCI format0-2.

Action 4:

The size alignment procedure may be completed if both of the followingconditions are fulfilled: (1) the total number of different DCI sizesconfigured to monitor may be no more than 4 for the cell; and (2) thetotal number of different DCI sizes scrambled with C-RNTI configured tomonitor may be no more than 3 for the cell.

Otherwise, it may be disclosed to perform the following operations.

-   -   It may be disclosed to remove the padding bit (if any)        introduced in Action 2 above.    -   It may be disclosed to determine the DCI format 1-0 monitored in        the USS based on the given configuration (e.g.,        SearchSpace-Config, PDCCH-Config) and/or RNTI, and the DCI        format size may be related to the size of the active DL BWP,        where active DL BWP is given by: (1) the size of the CORESET 0        if the CORESET 0 is configured for the cell; and (2) the size of        the initial DL BWP if the CORESET 0 is not configured for the        cell.    -   It may be disclosed to determine the DCI format 0-0 monitored in        the USS based on the given configuration (e.g.,        SearchSpace-Config, PDCCH-Config) and/or RNTI, and the DCI        format size may be related to the size of the initial UL BWP.    -   If the number of information bits in the DCI format 0-0        monitored in the USS prior to padding is less than the payload        size of the DCI format 1-0 monitored in the USS for scheduling        the same serving cell, a number of zero padding bits may be        generated for the DCI format 0-0 monitored in the USS until the        payload size equals that of the DCI format 1-0 monitored in the        USS.    -   If the number of information bits in the DCI format 0-0        monitored in the USS prior to truncation is larger than the        payload size of the DCI format 1-0 monitored in the USS for        scheduling the same serving cell, the bit-width of the frequency        domain resource assignment field in the DCI format 0-0 may be        reduced by truncating the first few most significant bits such        that the size of the DCI format 0-0 monitored in the USS equals        the size of the DCI format 1-0 monitored in the USS.

In some of the embodiments, the UE may be not expected to handle aconfiguration that, after applying the above actions, results in eitherone of the scenarios: (1) the total number of different DCI sizesconfigured to monitor may be more than 4 for the cell; (2) the totalnumber of different DCI sizes scrambled with C-RNTI configured tomonitor may be more than 3 for the cell; (3) the size of the DCI format0-0 in one USS may be equal to that of DCI format 0-1 in the same oranother USS; (4) the size of the DCI format 0-2 in one USS may be equalto that of DCI format 0-1 in the same or another USS; (5) the size ofthe DCI format 1-0 in one USS may be equal to that of DCI format 1-1 inthe same or another USS; or (6) the size of DCI format 1-2 in one USSmay be equal to that of DCI format 1-1 in the same or another USS.

In some of the embodiments, the DCI budget is equal to ‘4+1’. In oneexample, if the DCI budget ‘4+1’ is applied, the payload size of the DCIformat 1-0 equals that of the DCI format 0-0; and the payload size ofthe DCI format 1-2 equals that of the DCI format 0-2. Detailedimplementations are presented in Table 6.

TABLE 6 non- C-RNTI (size 1) or C-RNTI C-RNTI C-RNTI C-RNTI C-RNTI (size2) (size 3) (size 4) (size 5) DCI Monitored Monitored format in CSS inUSS 0-0 or USS Apply Apply configured initial UL BWP UL BWP DCIMonitored format in USS 0-1 Apply configured UL BWP DCI Monitored formatin USS 0-2 Apply configured UL BWP DCI Monitored Monitored format in CSSin USS 1-0 Apply Apply size of configured CORESET UL BWP 0 or initial DLBWP DCI Monitored format in USS 1-1 Apply configured DL BWP DCIMonitored format in USS 1-2 Apply configured DL BWP

Also, in one example, if the DCI budget ‘4+1’ is applied, regardless ofwhether DCI format 1-0/0-0 is monitored in the CSS or in the USS, thepayload size of the DCI format 1-0 may equal that of the DCI format 0-0monitored in the CSS. In other words, it may be disclosed to determinethe DCI format 1-0/0-0 monitored in the USS where the BWP is given bythe initial BWP or the size of CORESET 0. Example implementations arepresented in Table 7.

TABLE 7 non- C-RNTI (size 1) or C-RNTI C-RNTI C-RNTI C-RNTI C-RNTI (size2) (size 3) (size 4) (size 5) DCI Monitored format in CSS 0-0 or USS(C-RNTI) Apply initial UL BWP DCI Monitored format in USS 0-1 Applyconfigured UL BWP DCI Monitored format in USS 0-2 Apply configured ULBWP DCI Monitored format in CSS 1-0 or USS (C-RNTI) Apply size ofCORESET 0 or initial DL BWP DCI Monitored format in USS 1-1 Applyconfigured DL BWP DCI Monitored format in USS 1-2 Apply configured DLBWP

In some of the embodiments, the DCI size budget may be equal to ‘3+2’.In one example, there may be DCI formats configured outside the activetime (e.g., the DCI format 2-6) then the DCI budget ‘3+2’ may beapplied. The DCI size alignment procedure for a DCI format scrambled byC-RNTI may refer to the procedure mentioned in the above paragraph,which is omitted hereinafter for brevity.

In one aspect of this example, the payload size of the DCI formatoutside the active time may equal that of the DCI format scrambled bynon-C-RNTI inside the active time. For example, if there are more thantwo different DCI format sizes outside the active time, the DCI format2-6 scrambled with PS-RNTI may have the same payload size as the DCIformat 2-0 scrambled with Slot Format Indication (SFI)-RNTI, the DCIformat 2-1 scrambled with Interruption (INT)-RNTI, the DCI format 2-4scrambled with Cancellation Indication (CI)-RNTI, the DCI format 1-0scrambled with non-C-RNTI, or the DCI format 0-0 scrambled withnon-C-RNTI. Alternatively, the DCI format 2-1 scrambled with INT-RNTIand the DCI format 2-4 scrambled with CI-RNTI may have the same payloadsize.

In some of the embodiments, it may be disclosed to consider the impactfrom the configurable bit-field. First, it may be disclosed to considerthe DAI corresponding to a DAI field, which may include a counter DAI(cDAI) field and/or a total DAI (tDAI) field. Furthermore, a value ofthe cDAI field in DCI formats denotes the accumulative number of{serving cell, PDCCH monitoring occasion}-pair(s) in which PDSCHreception(s) or SPS PDSCH release associated with the DCI formats ispresent up to the current serving cell and current PDCCH monitoringoccasion. A value of the tDAI field, when present, in a DCI formatdenotes the total number of {serving cell, PDCCH monitoringoccasion}-pair(s) in which PDSCH reception(s) or SPS PDSCH releaseassociated with DCI formats is present, up to the current PDCCHmonitoring occasion m and is updated from PDCCH monitoring occasion toPDCCH monitoring occasion. Besides, a UE may assume a same value of tDAIin all DCI formats that include a tDAI field in PDCCH monitoringoccasion m. A UE does not expect to multiplex, in a same Type-2 HARQ-ACKcodebook, HARQ-ACK information that is in response to detection of DCIformats with different number of bits for the cDAI field.

In one example illustrating a wireless communication system thatincludes at least one BS and one UE, the UE may receive, from the BS, aradio resource control (RRC) message including information forconfiguring a HARQ-ACK codebook list, a first DCI, and a second DCI,where the HARQ-ACK codebook list includes a first HARQ-ACK codebookindicated by the first DCI and a second HARQ-ACK codebook indicated bythe second DCI. Noticeably, a first priority of the first HARQ-ACKcodebook and a second priority of the second HARQ-ACK codebook aredifferent, and the first DCI and the second DCI have a same format. Inanother example, the UE may determine whether a size difference existsbetween a first DAI field of the first DCI and a second DAI field of thesecond DCI. In another example, the UE may insert at least one bit witha zero value into one of the first DAI field and the second DAI fieldwhen the size difference between the first DAI field of the first DCIand the second DAI field of the second DCI is determined, where theinserted at least one bit with the zero value forms a most significantbit in the first DAI field or in the second DAI field. Preferably, thefirst HARQ-ACK codebook and the second HARQ-ACK codebook have differenttypes, where the types refer to a semi-static type and a dynamic type,respectively. Specifically, if different types ofPDSCH-HARQ-ACK-Codebook are configured to the UE, the size of the DAIfield may be equal to the bit-width of the DAI field in the DCI forscheduling data corresponding to a Type2 HARQ-ACK codebook. For example,if the UE is configured with PDSCH-HARQ-ACK-Codebook=semi-static andPDSCH-HARQ-ACK-Codebook=dynamic in the PUCCH-Config, the number of bitsfor the DAI field in the DCI format for scheduling the PDSCH withsemi-static HARQ-ACK codebook may be zero and the number of bits for theDAI field in the DCI format for scheduling the PDSCH with dynamicHARQ-ACK codebook may be two or four.

Specifically, in one aspect of this example, ‘00’ or ‘0000’ may beconfigured to the DAI field in the DCI formats for scheduling the PDSCHwith a semi-static HARQ-ACK codebook. In other words, the UE may inserta number of bits, where each bit is set with the zero value, to the DAIfield in the corresponding DCI that has the smaller bit size. In anotheraspect of this example, ‘11’ or ‘1111’ may be configured to the DAIfield in the DCI formats for scheduling the PDSCH with a semi-staticHARQ-ACK codebook.

FIG. 1 is a flowchart illustrating a DCI format construction procedure10 performed by a BS according to an example implementation of thepresent disclosure. As illustrated in FIG. 1 , the DCI formatconstruction procedure 10 for the BS includes:

-   -   Action 100: Start.    -   Action 102: Configure a first DAI field of first DCI with a        first size and configure a second DAI field of second DCI with a        second size.    -   Action 104: Generate at least one bit with a zero value for one        of the first DAI field and the second DAI field if a size        difference between the first size and the second size exists.    -   Action 106: Transmit, to a UE, an RRC message, the first DCI,        and the second DCI.    -   Action 108: End.

Preferably, action 102 to action 106 of the DCI format constructionprocedure 10 may be applied to the UE and the BS. Since detailedoperations of the action 102 to action 106 have been comprehensivelydiscussed and/or introduced above, details of the related operations areomitted for brevity.

Second, implementations of the present disclosure are to consider thepriority indication field. In one example, if the priority indicationfield is configured in the DCI format for dynamic grant but the priorityindication field is not configured in the DCI format for configuredgrant, the size of the field may need to be the same to avoid ambiguitybetween (de)activation DCI and re-transmission DCI.

Specifically, in one aspect of this example, the bit-width of thepriority indication field between the (de)activation DCI and there-transmission DCI may be the same. For example, there may be 1bit-width in the DCI for dynamic grant, and ‘0’ may be padded for thisfield in the DCI for configured grant. Alternatively, in another aspectof this example, if the UE detects inconsistent information for priorityindication between different DCI formats or the same DCI formatsscrambled with different RNTI, the UE may discard the priorityinformation in the DCI formats.

Third, implementations of the present disclosure are to consider theTDRA field. In one example, if the Rel-16 PUSCH scheme is configured,the size of the TDRA field may be the minimum configured bit-widthbetween different DCI formats or the same DCI formats scrambled withdifferent RNTIs.

Fourth, implementations of the present disclosure are to consider the RVfield. In one example, the size of the RV field may be the maximumconfigured bit-width between different DCI formats or the same DCIformats scrambled with different RNTIs.

FIG. 2 illustrates a block diagram of a node 200 for wirelesscommunication according to an example implementation the presentdisclosure. As illustrated in FIG. 2 , the node 200 may include atransceiver 206, a processor 208, a memory 202, one or more presentationcomponents 204, and at least one antenna 210. The node 200 may alsoinclude a Radio Frequency (RF) spectrum band module, a BS communicationsmodule, an NW communications module, and a system communicationsmanagement module, input/output (I/O) ports, I/O components, and powersupply (not explicitly illustrated in FIG. 2 ). Each of these componentsmay be in communication with each other, directly or indirectly, overone or more buses 224. In one implementation, the node 200 may be a UEor a BS that performs various functions disclosed herein, for example,with reference to FIG. 1 .

The transceiver 206 having a transmitter 216 (e.g.,transmitting/transmission circuitry) and a receiver 218 (e.g.,receiving/reception circuitry) may be configured to transmit and/orreceive time and/or frequency resource partitioning information. In oneimplementation, the transceiver 206 may be configured to transmit indifferent types of subframes and slots, including, but not limited to,usable, non-usable, and flexibly usable subframes and slot formats. Thetransceiver 206 may be configured to receive data and control channels.

The node 200 may include a variety of computer-readable media.Computer-readable media may be any available media that may be accessedby the node 200 and include both volatile (and non-volatile) media andremovable (and non-removable) media. By way of example, and notlimitation, computer-readable media may include computer storage mediaand communication media. Computer storage media may include bothvolatile (and non-volatile) and removable (and non-removable) mediaimplemented according to any method or technology for storage ofinformation, such as computer-readable information.

Computer storage media includes RAM, ROM, EEPROM, flash memory (or othermemory technology), CD-ROM, Digital Versatile Disks (DVD) (or otheroptical disk storage), magnetic cassettes, magnetic tape, magnetic diskstorage (or other magnetic storage devices), etc. Computer storage mediadoes not include a propagated data signal. Communication media maytypically embody computer-readable instructions, data structures,program modules, or other data in a modulated data signal, such as acarrier wave or other transport mechanism, and include any informationdelivery media. The term “modulated data signal” may mean a signal thathas one or more of its characteristics set or changed in such a manneras to encode information in the signal. By way of example, and notlimitation, communication media may include wired media, such as a wiredNW or direct-wired connection, and wireless media, such as acoustic, RF,infrared, and other wireless media. Combinations of any of the previousdisclosure should also be included within the scope of computer-readablemedia.

The memory 202 may include computer-storage media in the form ofvolatile and/or non-volatile memory. The memory 202 may be removable,non-removable, or a combination thereof. For example, the memory 202 mayinclude solid-state memory, hard drives, optical-disc drives, etc. Asillustrated in FIG. 2 , the memory 202 may store computer-readableand/or -executable instructions 214 (e.g., software codes) that areconfigured to, when executed, cause the processor 208 to perform variousfunctions disclosed herein, for example, with reference to FIG. 1 .Alternatively, the instructions 214 may not be directly executable bythe processor 208 but may be configured to cause the node 200 (e.g.,when compiled and executed) to perform various functions disclosedherein.

The processor 208 (e.g., having processing circuitry) may include anintelligent hardware device, a Central Processing Unit (CPU), amicrocontroller, an ASIC, etc. The processor 208 may include memory. Theprocessor 208 may process the data 212 and the instructions 214 receivedfrom the memory 202, and information through the transceiver 206, thebaseband communications module, and/or the NW communications module. Theprocessor 208 may also process information to be sent to the transceiver206 for transmission through the antenna 210, to the NW communicationsmodule for transmission to a CN.

One or more presentation components 204 may present data indications toa person or other device. Examples of presentation components 204 mayinclude a display device, speaker, printing component, vibratingcomponent, etc.

From the previous disclosure, it is manifested that various techniquesmay be used for implementing the concepts described in the presentdisclosure without departing from the scope of those concepts. Moreover,while the concepts have been disclosed with specific reference tocertain implementations, a person of ordinary skill in the art wouldrecognize that changes may be made in form and detail without departingfrom the scope of those concepts. As such, the disclosed implementationsare to be considered in all respects as illustrative and notrestrictive. It should also be understood that the present disclosure isnot limited to the particular disclosed implementations. Still, manyrearrangements, modifications, and substitutions are possible withoutdeparting from the scope of the present disclosure.

What is claimed is:
 1. A method performed by a Base Station (BS) forconstruction of a downlink control information (DCI) format, the methodcomprising: configuring a first downlink assignment index (DAI) field offirst DCI with a first size and configuring a second DAI field of secondDCI with a second size; generating at least one bit with a zero valuefor one of the first DAI field and the second DAI field if a sizedifference between the first size and the second size exists; andtransmitting, to a User Equipment (UE), a radio resource control (RRC)message, the first DCI, and the second DCI, wherein: the RRC messagecomprises information for configuring a Hybrid Automatic RepeatreQuest-ACKnowledge (HARQ-ACK) codebook list, the HARQ-ACK codebook listcomprises a first HARQ-ACK codebook indicated by the first DCI and asecond HARQ-ACK codebook indicated by the second DCI, and the first DCIand the second DCI have a same format.
 2. The method of claim 1, whereinthe generated at least one bit with the zero value forms a mostsignificant bit for the one of the first DAI field and the second DAIfield.
 3. The method of claim 1, wherein a first priority of the firstHARQ-ACK codebook and a second priority of the second HARQ-ACK codebookare different.
 4. The method of claim 1, wherein: the first HARQ-ACKcodebook and the second HARQ-ACK codebook have different types, and thetypes refer to a semi-static type and a dynamic type.
 5. A Base Station(BS) in a wireless communication system for construction of a downlinkcontrol information (DCI) format, the wireless communication systemcomprising a User Equipment (UE), the BS comprising: at least oneprocessor; and at least one memory coupled to the at least oneprocessor, wherein the at least one memory stores computer-executableinstructions that, when executed by the at least one processor, causethe BS to: configure a first downlink assignment index (DAI) field offirst DCI with a first size and configuring a second DAI field of secondDCI with a second size; generate at least one bit with a zero value forone of the first DAI field and the second DAI field if a size differencebetween the first size and the second size exists; and transmit, to theUE, a radio resource control (RRC) message, the first DCI, and thesecond DCI, wherein: the RRC message comprises information forconfiguring a Hybrid Automatic Repeat reQuest-ACKnowledge (HARQ-ACK)codebook list, the HARQ-ACK codebook list comprises a first HARQ-ACKcodebook indicated by the first DCI and a second HARQ-ACK codebookindicated by the second DCI, and the first DCI and the second DCI have asame format.
 6. The BS of claim 5, wherein the generated at least onebit with the zero value forms a most significant bit for the one of thefirst DAI field and the second DAI field.
 7. The BS of claim 5, whereina first priority of the first HARQ-ACK codebook and a second priority ofthe second HARQ-ACK codebook are different.
 8. The BS of claim 5,wherein: the first HARQ-ACK codebook and the second HARQ-ACK codebookhave different types, and the types refer to a semi-static type and adynamic type.